Conversation
This document outlines the requirements and expectations for a privacy-preserving bridge and cross-chain infrastructure, detailing functionality, security, usability, and team profile needed for development.
fryorcraken
left a comment
fryorcraken
left a comment
There was a problem hiding this comment.
A couple of things to fix before merge:
-
Wrong file path: The file is placed at
RFPs/RFPs/RFP-003-...(doubleRFPs/). Please move it toRFPs/RFP-003-bridges-cross-chain-infrastructure.md. -
README not updated: Please add RFP-003 to the summary table in
README.mdbetween theRFP_TABLE_START/RFP_TABLE_ENDmarkers.
|
Note: the license section in |
|
The title (and scope) is very broad. Before this RFP moves forward, we should discuss and decide what specific type(s) of bridges we want to see — e.g., Ethereum-only vs. multi-chain, lock-and-mint vs. burn-and-mint, trustless ZK light client vs. relayer-based, etc. |
|
Reading through this, It's presenting Logos as a "Privacy Preserving L1" we should be very clear here that the L1 is not the target for these atomic swaps. These atomic swaps are done against LEZ. It's a more complicated story but we should make it clear what the goal is: LEZ is where we have privacy preserving programmable money, the L1 is the settlement layer for Zones. |
3 participants
This document outlines the requirements and expectations for a privacy-preserving bridge and cross-chain infrastructure, detailing functionality, security, usability, and team profile needed for development.